Radio resource measurement techniques in directional wireless networks

ABSTRACT

Techniques for radio resource measurement (RRM) that support directionality, as well as scheduled media access techniques are described. For instance, a measurement request may be transmitted from a first device to a second device. This measurement request directs the second device to take one or more measurements of a wireless channel. Various characteristics for the one or more measurements may be included in the measurement request. For example, the measurement request may indicate at least one directional parameter and at least one timing parameter for the one or more measurements. In response to the request, the first device receives a measure report that includes measured values for each of the one or more measurements.

BACKGROUND

Wireless networks, such as wireless personal area networks (WPANs), wireless local area networks (WLANs), and/or cellular telephony networks provide for a wide array of mobile communications services. Currently, wireless networks are under development for the 60 GHz radio frequency (RF) band. Such networks intend to provide higher data rates, spatial reuse (enabled by the directional propagation properties of 60 GHz signals), directional communications, enhanced interference mitigation, and network stability.

In addition, it is planned for 60 GHz wireless networks to employ scheduled media access control (MAC) techniques, such as time division multiple access (TDMA). However scheduled media access techniques are typically not as robust as contention-based media access techniques. For example, carrier sense multiple access with collision avoidance (CSMA/CA) (which is currently employed in IEEE 802.11 networks) is often more robust in handling transmission interference.

Thus, it is desirable to ensure network robustness when scheduled MAC techniques, such as TDMA, are employed. One way to promote robustness involves the exchange of information between devices regarding the wireless environment. More particularly, such information provides for scheduled allocations that promote robust network operation.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the reference number. The present invention will be described with reference to the accompanying drawings, wherein:

FIG. 1 is a diagram of an exemplary operational environment;

FIG. 2 is a diagram of an exemplary transmission arrangement between two devices;

FIG. 3 is a logic flow diagram;

FIG. 4 is a diagram of an exemplary channel quality histogram request format;

FIG. 5 is a diagram of an exemplary channel quality histogram report format; and

FIG. 6 is a diagram of an exemplary device implementation.

DETAILED DESCRIPTION

Embodiments provide techniques for radio resource measurement (RRM) that support directionality, as well as scheduled media access techniques. For instance, embodiments may transmit a measurement request from a first device to a second device that directs the second device to take one or more measurements of a wireless channel. This measurement request may include various characteristics for the one or more measurements. For example, the measurement request may indicate at least one directional parameter and at least one timing parameter for the one or more measurements. In response to the request, the first device receives a measure report that includes measured values for each of the one or more measurements.

Conventional RRM techniques do not support directionality and scheduled access (e.g., TDMA). For instance, the Institute of Electrical and Electronics Engineers (IEEE) 802.11k Amendment to the IEEE 802.11-2007 Standard provides RRM schemes. However, these schemes were developed under the assumption of a CSMA/CA MAC and an omni-directional transmission mode.

Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

FIG. 1 is a diagram of an exemplary operational environment 100 that may employ the techniques described herein. This environment includes a central controller device (PCP) 102, and multiple stations (STAs) 104 a-d. These devices may be implemented in any combination of hardware and/or software. In general operation, these devices may communicate wirelessly with each other. Moreover, in embodiments, these devices may employ multiple beams and/or directional transmissions.

PCP 102 performs various control operations, including resource allocations for STAs 104 a-d. In particular, PCP 102 may manage resources within a repeating period called a TDMA frame (also known as Beacon Interval or Superframe). This may involve allocating time slots within the TDMA frame to STAs 104 a-d. Such allocations may employ spatial reuse. More particularly, such allocations may overlap (completely or partially) in time.

In embodiments, allocations made by PCP 102 may be based on requests received from STAs 104 a-d. In making such allocations, PCP 102 may consider characteristics regarding the wireless environment of STAs 104 a-d. Details involving the determination of such characteristics are provided below.

STAs 104 a-d may wirelessly communicate in accordance with resource allocations performed by PCP 102. These communications may involve transmissions between STAs 104. Also, these communications may involve exchanging transmissions with PCP 102. For example, PCP 102 may relay communications traffic between STAs. Further, PCP 102 may provide STAs 104 a-d with access to one or more wireless networks (e.g., the Internet and/or wired telephony networks).

As described above, PCP 102 may consider characteristics regarding the wireless environment of STAs 104 a-104 d. To determine such characteristics, PCP 102 may gather information from STAs 104 a-d. More particularly, PCP 102 may transmit requests to STAs 104 a-d. Each of such requests may direct the receiving STA to conduct particular measurements. In turn, the recipient STA conducts the measurement(s) and transmits a report back to PCP 102. From such reports, PCP 102 may perform resource allocations that consider factors, such as interference mitigation, network stability, and so forth. For example, based on such received report(s), PCP 102 may determine whether to make allocations involving spatial reuse.

As example of such features, FIG. 1 shows PCP 102 sending measurement requests 120 a and 120 b to STA 104 a and 104 b, respectively. In response, STAs 104 a and 104 b send measurement reports 122 a and 122 b to PCP 102. These messages are shown for purposes of illustration, and not limitation. Thus, messages may be sent to any combination of STAs 104 a-d in any number and/or sequence.

In embodiments, a device (e.g., PCP 102) may make allocations based on the amount of isolation among particular beams (as well as other information). For example, a beam pairing must exhibit a sufficiently low amount of isolation to support a wireless link. Further, the device may use such isolation information to establish multiple allocations that reuse resources (e.g., time and/or frequency and/or space). More particularly, information included in such measurement reports may be used to establish a high degree of isolation between each allocation (so that the interference is effectively managed). Examples of varying isolation levels are illustrated below with reference to FIG. 2.

FIG. 2 is a diagram showing an exemplary wireless arrangement between two devices. In particular, FIG. 2 shows a first station (“STA A”) and a second station (“STA B”). These stations may be employed in the context of FIG. 1 (e.g., each as one STAs 104 a-d).

Between these stations are multiple beams. For instance, FIG. 2 shows that STA A provides transmit beams 202 a-c. Also, FIG. 2 shows that STA B provides receive beams 204 a-c. These features are shown for purposes of illustration and not limitation. Through beams 202 a-c, STA A may engage in one or more directional transmissions. Similarly, through beams 204 a-c, STA B may receive transmissions from different directions.

FIG. 2 shows nine different pairings of transmit and receive beams between STA A and STA B. Each of these pairings exhibits different levels of isolation. For instance, there is a low amount of isolation between beams 202 a and 204 a. This is because these beams are substantially aligned (or overlapping). In contrast, there is a high amount of isolation between beams 202 c and 204 c. This is because these beams are unaligned (or non-overlapping). In embodiments, such levels of isolation may be determined through measurements performed by stations (e.g., STAs 104 a-d). Such measurements may be made in response to requests made by a controlling station (e.g., PCP 102).

Operations for the embodiments may be further described with reference to the following figures and accompanying examples. Some of the figures may include a logic flow. Although such figures presented herein may include a particular logic flow, it can be appreciated that the logic flow merely provides an example of how the general functionality as described herein can be implemented. Further, the given logic flow does not necessarily have to be executed in the order presented unless otherwise indicated. In addition, the given logic flow may be implemented by a hardware element, a software element executed by a processor, or any combination thereof. The embodiments are not limited to this context.

FIG. 3 illustrates an embodiment of a logic flow. In particular, FIG. 3 illustrates a logic flow 300, which may be representative of operations executed by one or more embodiments. This flow is described in the context of FIG. 1. However, this flow may be employed in other contexts.

At a block 302, a first device wirelessly sends a measurement request to a second device. This request directs the second device to perform one or more measurements of a wireless channel. The first device may be a coordinator device for a wireless network (e.g., PCP 102), and the second device may be a user device (e.g., one of STAs 104 a-d). In embodiments, this request may be a quality histogram request, as described below with reference to FIG. 4. However, embodiments may employ other request formats.

The request may specify one or more characteristics for these one or more measurements. For instance, the request may indicate particular directional and timing characteristics for the measurement(s). Examples of directional characteristics include (but are not limited to) a particular remote device to which the measurement(s) are to be directed, and a beam (e.g., a receive beam) through which the second device is to perform the measurement(s). Examples of timing characteristics include (but are not limited to) a measurement start time, a measurement period duration, and a number of measurements to be taken during the measurement period.

Further, the request may specify when the type of measurement(s) to be taken. Exemplary measurement types include a determination of an Average Noise plus Interference Power Indicator (ANIPI), and/or determination of a Received Signal to Noise Indicator (RSNI). Embodiments, however, are not limited to these measurement types

At a block 304, the second device wirelessly receives the measurement request. Following this, at a block 306, the second device performs one or more measurements in accordance with the request.

At a block 308, the remote device wirelessly sends a response (also referred to as a measurement report) to the first device containing the measurement(s). In embodiments, this response may be a quality histogram report, as described below with reference to FIG. 5. However, embodiments may employ other response formats.

The first device receives the response at a block 310. Then, at a block 312, the first device may make one or more resource allocations based on information provided in the response. As described above with reference to FIG. 1, this may involve allocating one or more time slots within a TDMA frame. However, embodiments are not limited to TDMA media access techniques.

FIG. 4 is a diagram showing an exemplary format 400 of a channel quality histogram format request. This format includes multiple fields. For instance, a regulatory class field 402 provides information regarding regulated parameters, such as channel frequency, channel spacing, power limits, and so forth. A channel number field 404 provides information regarding the channel for which measurements are to be taken. Embodiments may format fields 402 and 404 in accordance with Annex J of the IEEE 802.11k Amendment to the IEEE 802.11-2007 Standard. Each of fields 402 and 404 may be one octet in size. However, other sizes may be employed.

As shown in FIG. 4, format 400 further includes a STAID field 406 and a Beam ID field 408. These fields introduce directionality support for RRM measurements.

More particularly, STAID field 406 indicates a STA (e.g., by its MAC address) towards which the RRM request applies. For example, if the measuring STA is beamformed with the STA identified by STAID field 406, then the measurement shall be carried out directionally towards identified STA. In embodiments, STAID field 406 may be set to a broadcast ID (BcastlD), in which case the measuring STA will do so through an omni directional pattern. STAID field 406 may be in various formats. For example, in embodiments, STAID filed 406 indicates a MAC address of a STA. FIG. 4 shows that STAID ID field 406 may be one octet in size, which may be an Association ID obtained by the STA once it associated with the PCP. However, other types of identifiers and sizes may be employed.

Beam ID field 408 indicates a beam for which the corresponding measurement request applies. For example, if source and destination STAs have multiple beams between them, Beam ID field 408 identifies one of them. A value of zero (0) in this field indicates that any beam may be used for this measurement. As indicated in FIG. 4, Beam ID field 408 may be one octet in size. However, other sizes may be employed.

Measurement method field 410 indicates the method to be used by the measuring STA in carrying the measurement request, as well as in reporting back to the PCP in the corresponding measurement report. In embodiments, the conventions provided in the IEEE 802.11k Amendment to the IEEE 802.11-2007 Standard may be employed. For example, when field 410 is set to zero (0), Average Noise plus Interference Power Indicator (ANIPI) is designated. However, when this field is set to one (1), Received Signal to Noise Indicator (RSNI) is designated. Other values of measurement field 410 may be reserved for other designations. Measurement method field 410 may be one octet in size. However, other sizes may be employed. Moreover, embodiments are not limited to ANIPI and RSNI. Thus, in embodiments, measurement method field 410 may indicate other measurement types.

Measurement start time field 412 provides RRM support for scheduled access MAC protocols (e.g., TDMA). In the IEEE 802.11k Amendment to the IEEE 802.11-2007 Standard, no Measurement Start Time is defined. Rather a Randomization Interval is included which suits a CSMA/CA MAC protocol. However, for scheduled MAC protocols, a specific Measurement Start Time field is required. Thus, measurement start time field 412 indicates a time when the requested measurement is to commence. In embodiments, a value of 0 indicates that the requested measurement shall start immediately. Measurement start time field 412 may be eight octets in size. However, other sizes may be employed.

Measurement duration field 414 indicates a duration of the requested measurement. In embodiments, such duration may be either mandatory or preferred. As indicated in FIG. 4, measurement duration field may be two octets in size.

Number of time blocks field 416 provides a capability that is advantageous for spatial reuse and interference mitigation, but which is not currently supported in the IEEE 802.11k Amendment to the IEEE 802.11-2007 Standard. In particular, this field indicates the number of time blocks within the total Measurement Duration. A ratio between the measurement duration and the number of time blocks (i.e., the measurement duration divided by the number of Time blocks) provides a duration of each individual measurement to be conducted (also referred to as a measurement unit). As indicated in FIG. 4, field 416 may be one octet in size. However, other sizes may be employed.

In addition to the above fields, format 400 may include a field 418 (of variable size) to convey optional information sub-elements. In embodiments, this field may employ the same convention, as provided by the IEEE 802.11k Amendment to the IEEE 802.11-2007 Standard.

FIG. 5 is a diagram showing an exemplary format 500 of a channel quality histogram format report. This format includes multiple fields. For instance, regulatory class field 502 and channel number field 504 provide information, as described above with reference to fields 402 and 404 of FIG. 4. This information may be formatted as defined in Annex J of the IEEE 802.11k Amendment to the IEEE 802.11-2007 Standard. Each of fields 502 and 504 may be one octet in size. However, other sizes may be employed.

STAID field 506 and Beam ID field 508 indicate the directionality aspect of the measurement report, as described above with reference to fields 406 and 408 of FIG. 4. For instance, STAID field 506 indicates the STA towards which the measurement applies and Beam ID field 508 indicates the beam that was used to perform the measurement. As indicated in FIG. 5, STAID field 506 and Beam ID field 508 may each be one octet in size. However, other sizes may be employed.

Measurement method field 510, measurement start time field 512, measurement duration field 514, and number of time blocks 516 are employed as described above with reference to fields 410-416 of FIG. 4.

FIG. 5 shows that format 500 includes multiple measurement fields. In particular, FIG. 5 shows measurement fields 518 ₁-518 _(N) that correspond to each of N time blocks specified in the corresponding channel quality histogram request. Each of measurement fields 518 ₁-518 _(N) carries an actual measured value (e.g., an ANIPI value or an average RSNI value).

In addition to the above fields, format 500 may include a field 518 (of variable size) to convey optional information sub-elements. In embodiments, this field may employ the same convention, as provided by the IEEE 802.11k Amendment to the IEEE 802.11-2007 Standard.

FIG. 6 is a diagram of an implementation 600 that may be included in a wireless device, such PCP 102 and/or STAs 104 a-d of FIG. 1. This implementation, however, may be also employed in other contexts. Implementation 600 may include various elements. For example, FIG. 6 shows implementation 600 including multiple antennas 602 a-c, a transceiver module 604, a host module 606, a measurement module 607, and a resource allocation module 608. These elements may be implemented in hardware, software, or any combination thereof.

Antennas 602 a-c provide for the exchange of wireless signals with remote devices. Although three antennas are depicted, any number of antennas may be employed. Also, embodiments may employ one or more transmit antennas and one or more receive antennas. Such multiple antenna arrangements may be employed for beamforming. For instance, a weight may be set in each antenna may such that the combined output signal provides a corresponding beam.

As shown in FIG. 6, transceiver module 604 includes a transmitter portion 610, and a receiver portion 612. During operation, transceiver module 604 provides an interface between antennas 602 a-c and other elements, such as host module 606, measurement module 607, and/or resource allocation module 608. For instance, transmitter portion 610 receives symbols from such elements, and generates corresponding signals for wireless transmission by one or more of antennas 602 a-c. This may involve operations, such as modulation, amplification, and/or filtering. However, other operations may be employed.

Conversely, receiver portion 612 obtains signals received by one or more of antennas 602 a-c and generates corresponding symbols. In turn, these symbols may be provided to elements, such as host module 606, measurement module 607, and/or resource allocation module 608. This generation of symbols may involve operations, including (but not limited to) demodulation, amplification, and/or filtering.

The signals generated and received by transceiver module 604 may be in various formats. For instance, these signals may be modulated in accordance with an orthogonal frequency division multiplexing (OFDM) scheme or a Single Carrier (SC) scheme. However, other schemes and formats (e.g., QPSK, BPSK, FSK, etc.) may be employed.

To provide such features, transmitter portion 610 and receiver portion 612 may each include various components, such as modulators, demodulators, amplifiers, filters, buffers, upconverters, and/or downconveters. Such components may be implemented in hardware (e.g., electronics), software, or any combination thereof.

The symbols exchanged between transceiver module 604 and other elements may form messages or information associated with one or more protocols, and/or with one or more user applications. Thus, these elements may perform operations corresponding to such protocol(s) and/or user application(s). Exemplary user applications include telephony, messaging, e-mail, web browsing, content (e.g., video and audio) distribution/reception, and so forth.

Moreover, in transmitting and receiving signals, transceiver module 604 may employ various access techniques. For example, transceiver module 604 may employ a scheduled MAC technique, such as TDMA. Embodiments, however, are not limited to such techniques.

Measurement module 607 may perform measurements of wireless resources. Such resources may be specified in accordance with requests received (through transceiver module 604) from a remote device, such as PCP 102 or an IEEE 802.11 access point (AP). As described above, such measurements may be of average noise plus interference power (to provide an ANIPI), and/or of received signal to noise Indicator (to provide an RSNI). However, embodiments are not limited to these measurements. Thus, other wireless channel measurements (e.g., measurements involving any combination of signal power, interference power, and/or noise power) may be made.

Measurements made by measurement module 607 may be from hard symbols received from transceiver module 604 (e.g., based on a bit error rate determined through comparison with a predetermined sequence). Also, such measurements may be based on soft symbols generated by transceiver module 604 from received wireless signals. Moreover, such measurements may be generated from un-demodulated signals provided by transceiver module.

In addition, measurement module 607 may generate a report message that indicates such measurements. This report may be transmitted to the remote device through transceiver module 604.

In embodiments, resource allocation module 608 may perform resource allocation techniques described herein. For example, based on received measurements, allocation module 608 may allocate portions of a communications resource (e.g., time slots within a TDMA frame). Such allocation may include employ reuse that where sufficient isolation exists. Such isolation may be determined through measurements received from remote stations (through transceiver module 604). Allocations may be communicated to remote devices (through transceiver module 604) in control messages.

As described herein, various embodiments may be implemented using hardware elements, software elements, or any combination thereof. Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth.

Examples of software may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof.

Some embodiments may be implemented, for example, using a storage medium or article which is machine readable. The storage medium may store an instruction or a set of instructions that, if executed by a machine, may cause the machine to perform a method and/or operations in accordance with the embodiments. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software.

The storage medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, for example, memory, removable or non-removable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, and the like, implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.

While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not in limitation. For example, the techniques described herein are not limited to IEEE 802.11 networks. Thus, these techniques may be employed in other networks, such as ones that employ any combination of directional transmissions, reuse, and/or scheduled media access techniques.

Accordingly, it will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the invention. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. 

The invention claimed is:
 1. A method, comprising: transmitting a measurement request from a first device to a second device, the measurement request directing the second device to take one or more measurements of a wireless channel; receiving at the first device, a measure report in response to the request, the report comprising measured values for each of the one or more measurements; wherein the measurement request indicates at least one directional parameter and at least one timing parameter for the one or more measurements, wherein the at least one timing parameter includes a start time for the one or more measurements, a duration of a measurement period, and a number of measurements to be taken during the measurement period; wherein the at least one directional parameter includes an identifier of a remote device towards which the one or more measurements are to be directed, and an identifier of a beam through which the second device is to perform the one or more measurements.
 2. The method of claim 1, wherein the measurement request indicates a measurement type for the one or more measurements.
 3. The method of claim 2, wherein the measurement type is an Average Noise plus Interference Power Indicator (ANIPI).
 4. The method of claim 2, wherein the measurement type is a Received Signal to Noise Indicator (RSNI).
 5. The method of claim 1, further comprising allocating a wireless resource based at least on the measurement report.
 6. The method of claim 5, wherein allocating the wireless resource comprises allocating one or more time slots within a time interval.
 7. An apparatus, comprising: a transceiver configured to exchange wireless signals with one or more remote devices; and a measurement module configured to perform one or more measurements of a wireless channel in accordance with a measurement request message received from a remote device through the transceiver; wherein the measurement request indicates at least one directional parameter and at least one timing parameter for the one or more measurements, wherein the at least one directional parameter includes an identifier of a remote device towards which the one or more measurements are to be directed, and an identifier of a beam through which the second device is to perform the one or more measurements, and wherein the at least one timing parameter includes a start time for the one or more measurements, a duration of a measurement period, and a number of measurements to be taken during the measurement period.
 8. The apparatus of claim 7, wherein the measurement module is configured to transmit a measurement report to the remote device through the transceiver, the report comprising measured values for each of the one or more measurements.
 9. The apparatus of claim 7, wherein the measurement request indicates a measurement type for the one or more measurements.
 10. The apparatus of claim 9, wherein the measurement type is an Average Noise plus Interference Power Indicator (ANIPI).
 11. The apparatus of claim 9, wherein the measurement type is a Received Signal to Noise Indicator (RSNI).
 12. An apparatus, comprising: a transceiver configured to exchange wireless signals with one or more remote devices; and a resource allocation module configured to transmit a measurement request to a remote device through the transceiver, the measurement request directing the remote device to take one or more measurements of a wireless channel, and receive a measure report in response to the request, the report comprising measured values for each of the one or more measurements; wherein the measurement request indicates at least one directional parameter and at least one timing parameter for the one or more measurements; wherein the at least one directional parameter includes an identifier of a further remote device towards which the one or more measurements are to be directed, and an identifier of a beam through which the remote device is to perform the one or more measurements, and wherein the at least one timing parameter includes a start time for the one or more measurements, a duration of a measurement period, and a number of measurements to be taken during the measurement period.
 13. The apparatus of claim 7, wherein the resource allocation module is configured to allocate a wireless resource based at least on the measurement report.
 14. The apparatus of claim 13, wherein the wireless resource includes a time slot within a time interval. 